Skip to main content

UserMetaData How To's

How to's for the UserMetaData guide.

How to Use UserMetadata?​

How to Use UserMetadata?​

The following steps should be followed to add and configure the UserMetadata object on a form.

Add the UserMetadata Object to the Form​

  1. Open the form design screen
  2. Navigate to the Toolbox panel
  3. Locate the UserMetadata object
  4. Drag and drop the object onto the form

Select the User Information to Display​

  1. Click on the UserMetadata object added to the form
  2. The Properties panel opens on the right side
  3. Select the information to be displayed from the Human Resources fields list
    • Example: Full Name, Department, Title, Email, etc.

Build and Publish the Project​

  1. From the top menu, run Run → Build
  2. Make sure the project is built without errors
  3. Publish the project

Verify in the Web Interface​

  1. Log in to the web interface using your username and password
  2. Open the relevant form from the menu
  3. Observe that the selected user information is automatically populated

Usage Example​

  • UserMetadata → Department selected
  • When the form is opened:
    “Information Technologies” is displayed automatically

The user cannot modify this field; it is display-only.

Tips​

  • UserMetadata fields are generally used as read-only
  • These fields can be referenced in form rules (Rule Manager)
  • Multiple UserMetadata objects can be used within the same form

Notes​

  • Values belong only to the currently logged-in user
  • No manual data entry is required
  • Runs automatically when the form is opened

What Is UserMetadata?​

What Is UserMetadata?​

UserMetadata is a form control that automatically retrieves and displays the system-defined user information of the user who opens or creates a form in the web interface.

With this control, developers can display information such as:

  • Username
  • Full Name
  • Department
  • Job Title
  • Email
  • Employee ID
  • Other Human Resources (HR) attributes directly from the system, without requiring manual data entry.

Main Purpose​

  • Eliminate repetitive user input
  • Prevent incorrect or inconsistent data entry
  • Make forms faster and more reliable
  • Create user-specific, auto-filled form fields

Where Is It Used?​

  • Request forms
  • Leave / advance / expense processes
  • Human Resources forms
  • Approval and workflow start screens
  • User-based reporting and record screens

Key Features​

  • Automatically retrieves the current user’s information
  • Direct access to Human Resources (HR) data
  • Ideal for read-only (display-only) usage
  • Data is displayed automatically when the form loads

Notes​

  • The UserMetadata control does not accept user input; it is for display purposes only
  • The information to be displayed is selected from the control’s Properties panel
  • Displayed data is automatically determined based on the logged-in user

How to Use Client Enabled?​

What is Client Enabled?​

Client Enabled is a property that defines whether a form control is active (enabled) on the client side when the form is first loaded.
If it is set to True, the control is immediately usable by the user.
If it is set to False, the control is disabled and cannot be interacted with until a specific condition or rule activates it.

This property is especially useful for controlling the user’s interaction flow and applying dynamic behaviors using the Rule Manager.

What Does It Do?​

The property allows developers to:

  • Control when a form control becomes interactive.
  • Prevent users from entering or changing data until prerequisites are met.
  • Dynamically enable or disable controls based on user input or logic.

Example Scenario — Conditional Activation​

Scenario:
A form contains a checkbox called “I Accept Terms” and a text field called “Signature.”
The goal is to make the “Signature” field inactive until the user checks “I Accept Terms.”

Steps to Implement:​

  1. Select the “Signature” field in the form editor.

  2. In the Properties panel, find the Client Enabled field.

  3. Set the value to False — the field will now be disabled by default when the form loads.

  4. Open the Rule Manager.

  5. Add a new rule:

    Condition:

Action:

  1. Save and publish the form.

Result:​

  • When the form loads, the “Signature” field is disabled.
  • Once the user checks “I Accept Terms,” the field automatically becomes active and editable.

Behavior Summary​

Property StateDescription
TrueThe control is active and ready for user interaction when the form loads.
FalseThe control is disabled at load time and can be enabled dynamically via rules or code.

Notes & Best Practices​

  • Use the Client Enabled property to manage client-side interactivity without requiring server actions.
  • Combine it with Rule Manager to define when and how controls become active.
  • Remember: if server enablement is disabled, the client cannot enable the control even if Client Enabled is set to True.
  • By default, this property is set to True (active).

Summary​

Client Enabled improves form usability by letting developers control when and how users interact with form controls.
It is essential for creating responsive, condition-based form experiences where user actions dynamically change the form’s state.